Skip to content

Conversation

@roomote
Copy link
Contributor

@roomote roomote bot commented Jul 30, 2025

Fixes #6432 - Windows debugging issue where VSCode debug configuration failed because the root turbo.json was missing the bundle and watch:bundle task definitions.

Problem

Users on Windows were unable to debug the extension in VSCode because:

  • VSCode debug configuration runs the default build task (watch)
  • The watch task depends on watch:bundle via turbo
  • Root turbo.json was missing bundle and watch:bundle task definitions
  • This caused "Cannot find module extension.js" error

Solution

Added the missing task definitions to root turbo.json:

  • bundle task with proper outputs configuration
  • watch:bundle task with cache disabled
  • Both tasks properly delegate to workspace-specific implementations

Testing

  • ✅ Verified npx turbo bundle works correctly
  • ✅ Verified npx turbo watch:bundle --dry-run recognizes the task
  • ✅ Confirmed extension.js is generated in src/dist/
  • ✅ All linting and type checks pass

This fix ensures that the VSCode debug configuration will work properly on Windows by making sure all required turbo tasks are defined at the root level.


Important

Adds missing bundle and watch:bundle tasks to turbo.json to fix Windows VSCode debugging issue.

  • Behavior:
    • Adds bundle and watch:bundle tasks to turbo.json to fix Windows VSCode debugging issue.
    • bundle task includes outputs configuration for dist/** and src/dist/**.
    • watch:bundle task has caching disabled.
  • Testing:
    • Verified npx turbo bundle and npx turbo watch:bundle --dry-run work correctly.
    • Confirmed extension.js is generated in src/dist/.
    • All linting and type checks pass.

This description was created by Ellipsis for fe87e25. You can customize this summary. It will automatically update as commits are pushed.

Fixes #6432 - Windows debugging issue where VSCode debug configuration
failed because the root turbo.json was missing the bundle and watch:bundle
task definitions that are required by the debug tasks.

The issue occurred because:
- VSCode debug configuration runs the default build task (watch)
- The watch task depends on watch:bundle via turbo
- Root turbo.json was missing bundle and watch:bundle task definitions
- This caused "Cannot find module extension.js" error on Windows

Changes:
- Added bundle task with outputs configuration
- Added watch:bundle task with cache disabled
- Both tasks now properly delegate to workspace-specific implementations
@roomote roomote bot requested review from cte, jr and mrubens as code owners July 30, 2025 14:45
@hannesrudolph hannesrudolph added the Issue/PR - Triage New issue. Needs quick review to confirm validity and assign labels. label Jul 30, 2025
Copy link
Contributor Author

@roomote roomote bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for this fix! This correctly addresses the Windows debugging issue by adding the missing turbo task definitions. I've reviewed the changes and have some suggestions to improve consistency and robustness.

"inputs": ["src/**", "package.json", "tsconfig.json", "tsup.config.ts", "vite.config.ts"]
},
"bundle": {
"outputs": ["dist/**", "src/dist/**"]
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The bundle task is missing inputs configuration. Should this include the same inputs as the build task (src/**, package.json, tsconfig.json, etc.) to ensure proper cache invalidation when source files change?

},
"bundle": {
"outputs": ["dist/**", "src/dist/**"]
},
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this intentional that the bundle task configuration is minimal compared to other tasks? For consistency, could it follow the same pattern as the build task with comprehensive inputs configuration?

@dosubot dosubot bot added size:XS This PR changes 0-9 lines, ignoring generated files. bug Something isn't working labels Jul 30, 2025
@daniel-lxs daniel-lxs moved this from Triage to PR [Needs Prelim Review] in Roo Code Roadmap Aug 1, 2025
@hannesrudolph hannesrudolph added PR - Needs Preliminary Review and removed Issue/PR - Triage New issue. Needs quick review to confirm validity and assign labels. labels Aug 1, 2025
@daniel-lxs
Copy link
Member

Closing, can't repro

@daniel-lxs daniel-lxs closed this Aug 5, 2025
@github-project-automation github-project-automation bot moved this from New to Done in Roo Code Roadmap Aug 5, 2025
@github-project-automation github-project-automation bot moved this from PR [Needs Prelim Review] to Done in Roo Code Roadmap Aug 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working PR - Needs Preliminary Review size:XS This PR changes 0-9 lines, ignoring generated files.

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

Failed to debug roo-code in vscode on Windows

4 participants